home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
deskjet.z
/
deskjet
Wrap
Text File
|
1998-10-30
|
12KB
|
265 lines
DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111))))
NNNNAAAAMMMMEEEE
deskjet - HP DeskJet/PaintJet parallel printer driver
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ddddeeeesssskkkkjjjjeeeetttt ----PPPP pppprrrriiiinnnntttteeeerrrrnnnnaaaammmmeeee [ options ] [ inputfile ]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
The _d_e_s_k_j_e_t driver is a printer-specific driver for a HP DeskJet 500C,
550C, 560C, 1200C or PaintJet XL300 printer connected to an SGI
/dev/plp-compatible parallel port. _d_e_s_k_j_e_t reads STIFF format image
files, writes PCL commands to the printer, and uses _l_i_b_p_o_d(_3) functions
to keep the printer object database (POD) current, thereby providing
feedback on any engine errors encountered.
The driver opens and maintains the POD files for the specified printer.
For more information on POD files refer to the _l_i_b_p_o_d(_3) and _p_o_d(_4) man
pages.
While ddddeeeesssskkkkjjjjeeeetttt has the parallel port open, no other driver may flock the
port, thus effectively reserving the printer for exclusive use by
cooperating drivers.
IIIINNNNPPPPUUUUTTTT FFFFIIIILLLLEEEE FFFFOOOORRRRMMMMAAAATTTT
ddddeeeesssskkkkjjjjeeeetttt assumes that its input is coming from standared input unless a
filename is specified after any and all command line options.
ddddeeeesssskkkkjjjjeeeetttt accepts the input files in planar as well as chunky STIFF 1-bit
format and supports K, CMY, CMYK colorspaces. STIFF is a streamable
subset of TIFF 6.0. For more information on the STIFF image file format,
see the _l_i_b_s_t_i_f_f(_3) man pages.
UUUUSSSSAAAAGGGGEEEE
----PPPP _p_r_i_n_t_e_r_n_a_m_e
Specifies the printer with which ddddeeeesssskkkkjjjjeeeetttt is communicating.
_p_r_i_n_t_e_r_n_a_m_e is the name under which the System V R3 spooler
recognizes the printer, as given on the llllpppp command line. This
option is required.
----eeee Specifies that driver should exit immediately on fault. By
default, the driver waits indefinitely for faults to clear,
retrying any errors every several seconds, where the exact
number of seconds is defined in the POD config error_retry_wait
entry. This option is useful when only a quick inquiry needs
to be performed.
PPPPaaaaggggeeee 1111
DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111))))
----ssss Specifies that the driver should exit after ascertaining
printer status and updating the POD status file. If an error
is encountered, however, ddddeeeesssskkkkjjjjeeeetttt may block unless the ----eeee switch
is given as well. If a quick status update is what you want,
invoke ddddeeeesssskkkkjjjjeeeetttt with both the ----ssss and the ----eeee options to insure
that ddddeeeesssskkkkjjjjeeeetttt exits promptly.
----wwww Specify this flag to suppress warning messages in the printer
status file. By default, warning messages such as the driver
version or other non-fatal errors are written to the printer
status file.
----DDDD Turns on debugging information. Five levels of debugging
information are supported: None, CoarseDetail, MediumDetail,
FineDetail, and EvenFinerDetail. These correspond to 0, 1, 2,
3, and 4 or more ----DDDD switches given on the command line. That
is, multiple ----DDDD options given on the command line result in
progressively more detailed debugging information.
----tttt Prints a test page and performs printer diagnostics. Use this
to verify that the printer, cables, and driver are functional.
This option is useful when trying to narrow down the location
of an error in printing. If this fails, either the printer,
the cable, or the driver (including the /dev/plp device driver)
is at fault, but the model file, print scheduler, and rendering
filters are not to blame.
----LLLL _l_o_g_f_i_l_e_n_a_m_e
Specifies a filename to which error and debug information
should be appended. If this option is not specified, error and
debug information is appended to stderr, which is generally
redirected by the System V spooler to /var/spool/lp/log.
----RRRR Reset the parallel port immediately after opening but before
using it. This is not the default, but can be a useful feature
for those recalcitrant printers. Note that some printers
ignore the RESET signal altogether. This includes most HP
DeskJets.
----3333 Force PCL3 mode. This disallows any commands specific to PCL4
or later. Specifically, PCL3 does not understand the number of
copies commands or any command which would require a full page
buffer in the printer: no such page buffer is kept in the
printer. If this switch is given, multiple copies will be sent
by complete retransmission rather than a PCL reprint command.
PPPPaaaaggggeeee 2222
DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111))))
----XXXX _H_o_r_i_z_o_n_t_a_l_R_e_s_o_l_u_t_i_o_n
Specifies the horizontal resolution at which to print, one of
the following: 75, 100, 150, or 300. The default is 300. This
is normally derived from the printer status database, but if
given, it overrides and will be written to the printer status
database.
----YYYY _V_e_r_t_i_c_a_l_R_e_s_o_l_u_t_i_o_n
Specifies the vertical resolution at which to print, one of the
following: 75, 100, 150, or 300. The default is 300. This is
normally derived from the printer status database, but if
given, it overrides and will be written to the printer status
database.
----SSSS _P_a_p_e_r_S_i_z_e
Specifies the papersize to request from the printer. This may
be any papersize recognized by libpod(3), _b_u_t _o_n_l_y _t_h_o_s_e _s_i_z_e_s
_l_i_s_t_e_d _i_n _t_h_e _p_r_i_n_t_e_r _c_o_n_f_i_g_u_r_a_t_i_o_n _f_i_l_e _s_h_o_u_l_d _b_e _u_s_e_d. _T_h_i_s
_i_s _n_o_r_m_a_l_l_y _d_e_r_i_v_e_d _f_r_o_m _t_h_e _p_r_i_n_t_e_r _s_t_a_t_u_s _d_a_t_a_b_a_s_e, _b_u_t _i_f
_g_i_v_e_n, _i_t _o_v_e_r_r_i_d_e_s _a_n_d _w_i_l_l _b_e _w_r_i_t_t_e_n _t_o _t_h_e _p_r_i_n_t_e_r _s_t_a_t_u_s
_d_a_t_a_b_a_s_e.
----OOOO _f_i_l_e_n_a_m_e
Output data to _f_i_l_e_n_a_m_e instead of the device port or standard
output. The data will not be printed; the data that would have
been sent to the printer had the ----OOOO option not been specified
will instead be saved to _f_i_l_e_n_a_m_e.
EEEEXXXXIIIITTTT CCCCOOOODDDDEEEESSSS
The driver normally exits with an exit code of zero (0), denoting no
error. A number of exit codes are supported to give more information
about unsuccessful exits. Remember that the driver will not exit on
recoverable errors unless the ----eeee switch is given.
The error codes 1 through 18 denote the following meanings, in order:
unknown error, bad command line or image header arguments, bad POD
database access, bad device name, bad device type, bad status update,
unsuccessful device access, bad memory reference, failed memory
allocation, invalid data format, invalid data header, short or empty
input data file, short or empty firmware download code file, bad or short
input data file, failed transmission, data buffer invalid, test print
failed, firmware download failed.
A common error exit is on empty input: the driver will return error code
12, indicating a short or empty input file, whenever the PostScript
interpreter (or another upstream filter) dies before a full page of data
was written to the driver. This can happen when bad PostScript code is
sent to be printed, for instance. In this case, the spooler log file
PPPPaaaaggggeeee 3333
DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo DDDDEEEESSSSKKKKJJJJEEEETTTT((((1111))))
(/var/spool/lp/log) should be consulted to determine which filter failed;
an error should have been written to this file by the dying filter or
driver.
CCCCAAAAVVVVEEEEAAAATTTTSSSS
ddddeeeesssskkkkjjjjeeeetttt will not exit on spooler job cancellation (SIGTERM) until its
input has been completely copied to the output device. This means that
if a printer is unable to accept data, cancelling the job will not kill
the ddddeeeesssskkkkjjjjeeeetttt process. To do so, you must explicitly kill the process with
SIGKILL (9). This behavior is required so that job cancellation does not
leave the printer in a wedged state: cancelling in the middle of a raster
page would leave many parallel printers in a bad state which could eat
several subsequent print jobs.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
psrip(1), impressario(1), printstatus(1), printpanel(1), libpod(3),
libspool(3), libstiff(3).
PPPPaaaaggggeeee 4444